Add docs about workflow re-execution after hibernation #25781
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was curious how local state was preserved across hibernations, so I tested it with a simple example using Math.random(). Turns out the entire workflow function re-executes from the start after hibernation, only step returns are preserved. It could have been that the state of the isolate was saved.
This isn't immediately obvious from the existing "Do not rely on state outside of a step" section, so I've added a new section that explicitly explains:
I also added a loop example which there is none of in the examples right now 😄